Methods and system for operating a mobile point-of-sales application using a sim

ABSTRACT

A method for operating a mobile Point-of-Sales (mPOS) application for executing a transaction includes: a Universal Integrated Circuit Card (UICC) card connected to a terminal device executes in interaction with the terminal device an application frontend of the mPOS application that provides, upon launch, an I/O interface with a human machine interface displayed by a touchscreen of the terminal device and a machine-to-machine interface; and the application frontend, for starting a transaction, captures transaction data associated with the transaction to be started via the human machine interface, reads further transaction data via the machine-to-machine interface from a transaction device separate from the terminal device and arranged close to the terminal device, generates a transaction authorization authorizing the requested transaction, and transmits the transaction authorization, the transaction data and the further transaction data via a connection to a remote backend server for completing the transaction.

CROSS-REFERENCE TO PRIOR APPLICATIONS

This application claims benefit to European Patent Application No. EP 21187 287.4, filed on Jul. 22, 2021, which is hereby incorporated byreference herein.

FIELD

The invention relates to methods for operating a mobile Point-of-Sales(mPOS) application in a communication network. Furthermore, theinvention relates to a system for operating a mobile Point-of-Sales(mPOS) application in a communication network.

BACKGROUND

A mPOS application is used for completing a purchase, particularly atransaction (e.g. a payment), and is usually executed on a COTS (Commonof the Shelf) device.

The mPOS application (i.e. the COTS device) is assigned to andconfigured for a particular user (e.g. a merchant). For operating a mPOSapplication, particularly for completing a transaction, the userprovides the COTS device with transaction data. The transaction data maybe automatically provided by the mobile point-of-sale (POS) applicationimplemented on the COTS device or manually provided by the useroperating a human machine interface of the COTS device (e.g. by hittinga keypad of the COTS device or by touching a keypad displayed by atouchscreen of the COTS device). The transaction data to be provided atleast comprises a transaction amount (e.g. an amount of moneycorresponding to a price of a product to be sold).

During a normal operation of the mPOS application, the mPOS applicationis executed by the COTS device that is connected via a connection to acommunication network. When the mPOS application is provided with thetransaction data, a further user (e.g. a customer) is required to checkthe provided transaction data, to provide further transaction data (e.g.data indicating an account to be debited) and to authorize thetransaction. The further user may provide a transaction devicecomprising the further transaction data (e.g. a payment card or afurther terminal device) for being read by the COTS device, andadditionally provide a personal key (e.g. a personal identificationnumber (PIN)) by operating the human machine interface of the COTSdevice (e.g. by hitting a keypad of the COTS device or by touching akeypad displayed by a touchscreen of the COTS device). When the providedpersonal key matches the transaction device the mPOS applicationconsiders the transaction to be authorized and completes the transactionby transmitting a transaction request indicating the transaction andcomprising the transaction data, the further transaction data and acorresponding transaction authorization via the connection to a remotenetwork server, particularly to a payment system as part of a paymentinfrastructure that is installed on the remote network server.

As described above, the further user has to have his transaction deviceread by the COTS device and to operate the COTS device for authorizingthe transaction. The further user may suffer from a certain discomfortor anxiety in presenting sensitive account data and/or a personal key.Such mPOS application is exposed to many attacks. An attack surface of astandard Android/iOS device is quite high. For this reason, mPOSsolutions on a COTS device are combined with an extensive externalmonitoring system, which guarantees the health of the device. However,this monitoring is complex and has a performance impact, too. Moreover,a mPOS application on a COTS device requires a complex setup andpersonalization procedure in which a respective merchant and the COTSdevice have to be verified remotely. These shortcomings may reduce awide acceptance of such methods and systems for completing atransaction, i.e. for operating a mPOS application.

SUMMARY

In an exemplary embodiment, the present invention provides a method foroperating a mobile Point-of-Sales (mPOS) application for executing atransaction. The method includes: a Universal Integrated Circuit Card(UICC) card connected to a terminal device executes in interaction withthe terminal device an application frontend of the mPOS application thatprovides, upon launch, an I/O interface with a human machine interfacedisplayed by a touchscreen of the terminal device and amachine-to-machine interface; and the application frontend, for startinga transaction, captures transaction data associated with the transactionto be started via the human machine interface, reads further transactiondata via the machine-to-machine interface from a transaction deviceseparate from the terminal device and arranged close to the terminaldevice, generates a transaction authorization authorizing the requestedtransaction, and transmits the transaction authorization, thetransaction data and the further transaction data via a connection to aremote backend server for completing the transaction.

BRIEF DESCRIPTION OF THE DRAWINGS

Subject matter of the present disclosure will be described in evengreater detail below based on the exemplary figures. All featuresdescribed and/or illustrated herein can be used alone or combined indifferent combinations. The features and advantages of variousembodiments will become apparent by reading the following detaileddescription with reference to the attached drawings, which illustratethe following:

FIG. 1 schematically shows a partial diagram of a system according tothe invention for operating a mPOS application.

DETAILED DESCRIPTION

Exemplary embodiments of the invention provide methods for operating amobile Point-of-Sales (mPOS) application which provides a securefrontend in the merchant's terminal device and, thus, safe protection ofboth sensitive data and health of the merchant's terminal device.Exemplary embodiments of the invention provide a system for operating amobile Point-of-Sales (mPOS) application.

A first aspect of the invention is a method for operating a mobilePoint-of-Sales (mPOS) application, the mPOS application comprisingexecuting a transaction, the method comprising at least the steps:

-   -   a UICC (Universal Integrated Circuit Card) card, particularly a        SIM card, connected to, particularly inserted in a terminal        device that is connected to a communication network via a        connection executes, in interaction with the terminal device, an        application frontend of the mPOS application that provides, upon        launch, an I/O (Input/Output) interface with a human machine        interface displayed by a touchscreen of the terminal device and        a machine-to-machine interface,    -   the application frontend, for starting a transaction, captures        transaction data associated with the transaction to be started        via the human machine interface and reads further transaction        data via the machine-to-machine interface from a transaction        device separate from the terminal device and arranged close to        the terminal device, generates a transaction authorization        authorizing the requested transaction, and transmits the        transaction authorization, the transaction data and the further        transaction data via the connection to a remote backend server        for completing the transaction.

Depending on a generation and type of an underlying system standard, alltypes of smart cards or smart card applications referred to as UICC,SIM, USIM (UMTS subscriber identity module), R-UIM (removable universalidentity module), eSIM (embedded subscriber identity module) or iSIM(integrated subscriber identity module) can be used in the presentinvention and herein are collectively referred to as a “UICC” card or asa “SIM” card.

A second aspect of the invention is a method for operating a mobilePoint-of-Sales (mPOS) application, the mPOS application comprisingexecuting a transaction, the method comprising at least the steps:

-   -   a backend server connected to a communication network executes        an application backend of the mPOS application,    -   a UICC smart card, particularly a SIM card, connected to,        particularly inserted in a terminal device that is connected to        the communication network via a connection executes, in        interaction with the terminal device, an application frontend of        the mPOS application that provides, upon launch, an I/O        interface with a human machine interface displayed by a        touchscreen of the terminal device and a machine-to-machine        interface,    -   the application frontend, for starting a transaction, captures        transaction data associated with the transaction to be started        via the human machine interface and transmits a transaction        request indicating the transaction to be started and comprising        the transaction data to the application backend via the        connection,    -   the application backend, upon receipt of the transaction        request, transmits an authorization request to the application        frontend via the connection,    -   the application frontend, upon receipt of the authorization        request, reads further transaction data via the        machine-to-machine interface from a transaction device separate        from the terminal device and arranged close to the terminal        device, generates a transaction authorization authorizing the        requested transaction, adds the read further transaction data to        the transaction authorization and transmits the transaction        authorization to the application backend via the connection, and    -   the application backend, upon receipt of the transaction        authorization and the transaction data, verifies the transaction        authorization and completes the transaction.

Completing the transaction may comprise transmitting a transactionconfirmation to the application frontend. The transaction confirmationindicates a success of the transaction or an error preventing a successof the transaction. The transaction confirmation may be transmitted tothe terminal device via a messaging service of the communicationnetwork, e.g. short message service (SMS).

The terminal device may be a dedicated terminal device or a generalterminal device (e.g. a smartphone or the like), which is operated by auser (e.g. a merchant). The terminal device and the backend server,particularly the application frontend executed by the terminal device incombination with the UICC card, and the application backend executed bythe backend server, communicate with each other via the connectionprovided by the communication network. The application backend completesthe transaction upon receipt of both the transaction request and thetransaction authorization. While the transaction request comprisestransaction data required for completing the transaction (e.g. an amountof money corresponding to a price of a product or account data), thetransaction authorization is caused by a personal key (e.g. a personalidentification number (PIN)), which is correctly provided via the humanmachine interface by a further user (e.g. a customer buying the productfrom the merchant).

In many embodiments of the invention, reading further transaction datavia the machine-to-machine interface comprises wirelessly reading thefurther transaction data from the further device using near fieldcommunication (NFC) or Bluetooth.

Preferably, reading further transaction data via the machine-to-machineinterface comprises reading account data as the further transaction dataand authorization data from a credit card or a debit card as thetransaction device and a payment is completed as the transaction.

In a preferred embodiment, the machine-to-machine interface isimplemented as a SWP (Single Wire Protocol) interface to a CLF(contactless frontend) chip of the terminal device for reading theaccount data and the authorization data from the credit card or debitcard. Generally, SPW as a contact based protocol provides an interfacebetween the CLF chip and the UICC (Universal Integrated Circuit Card)smart card, particularly the SIM (Subscriber Identity Module) card, andallows contactless communication. Generally, the UICC card, particularlythe SIM card, comprises eight pins, numbered as C1 to C8. The C1 pin andthe C5 pin are connected to the CLF chip for energy supply (i.e. toprovide an operating voltage to the SIM card), and the C6 pin of the SIMcard is connected to the CLF chip for SWP support.

Still preferably, the UICC card comprises a card application toolkit(CAT) allowing to build up the human machine interface. In the case thatthe UICC card is a SIM card, the SIM card comprises a STK (SIMapplication toolkit) as CAT, STK being specified in GSM 11.14. The SIMcard may be a classical SIM card, an eSIM (embedded SIM) or an iSIM(integrated SIM) or a USIM (universal SIM).

The UICC card, particularly the SIM card, acts as security enclave inthe application frontend and provides an end-to-end protected datachannel with the backend server, particularly with an edge cloud serveras the backend server.

In a further embodiment, generating the transaction authorizationcomprises capturing a personal key via the human machine interface andadding the captured personal key to the transaction authorization. Uponreceipt of the authorization request, the application frontend generatesthe transaction authorization by reading the further transaction datafrom the transaction device (e.g. a credit card or a debit card of afurther user, such as a merchant's customer) and by requiring a personalkey like a personal identification number (PIN) of the further user.

According to still a further embodiment, verifying the transactionauthorization comprises verifying whether the captured personal keymatches the transaction device and considering the transaction to beauthorized when the captured personal key matches the transactiondevice.

In many embodiments, the UICC card, particularly the SIM card,implements, using at least one encryption key, at least one secure datachannel on the connection between the terminal device and the backendserver. The transaction data and the personal key captured via the humanmachine interface as well as the further transaction data received viathe machine-to-machine interface are transmitted to the backend servervia the at least one secure data channel.

The application frontend executed on the terminal device in conjunctionwith the UICC smart card is provided with a first public private keypair for establishing the secure data channel on the connection betweenthe terminal device and the backend server. The first public private keypair comprises a first public key and a first private key.

The first public key of the first public private key pair may beprotected by a certificate signed by a trusted authority. The trustedauthority may issue and sign the certificate. The user of the terminaldevice (e.g. the merchant) may register with the trusted authority touse the mPOS application and/or to get the certificate signed by thetrusted authority.

For establishing the at least one secure data channel on the connection,the certificate is sent from the application frontend, particularly fromthe UICC smart card to the application backend and, upon verification ofthe certificate by the application backend, a second public private keypair with a second public key and a second private key is generated. Thesecond public key of the second public private key pair is sent from theapplication backend to the application frontend, particularly the UICCsmart card. At both the application frontend and the applicationbackend, a common symmetric encryption key based on the first and secondpublic private key pairs is created. To negotiate the common symmetricencryption key, a suitable asymmetric key exchange procedure (i.e. asuitable asymmetric key exchange protocol) is used. Known traditionalpublic-key cryptosystems (i.e. algorithms) of securely exchangingencryption keys are Diffie-Hellman key exchange (DH), (better:Diffie-Hellman-Merkle key exchange (DHM)), Diffie Hellman Elliptic Curve(DHEC) and RSA (Rivest-Shamir-Adleman). DH, DHEC and RSA are based onnumber theoretic methods. Both the application frontend (particularlythe UICC smart card) and the application backend use a combination ofthe public and private keys to negotiate the common symmetric encryptionkey that is finally used by both the application frontend at theterminal device and the application backend at the backend server tocommunicate with each other.

In still further embodiments, the UICC card, particularly the SIM cardimplements a first applet and a second applet, the first applet beingconfigured to receive the further transaction data via themachine-to-machine interface, particularly from a CLF chip of theterminal device via the SWP protocol, and the second applet beingconfigured to provide and operate the human machine interface forcapturing the transaction data entered by a user of the terminal deviceand/or a personal key of the user and/or a personal key of a furtheruser.

Preferably, both the first applet and the second applet are Java basedapplications that run securely on the UICC card, particularly the SIMcard. The security is guaranteed by the underlying Java Card technology.

Generally, known symmetric key algorithms, known asymmetric keyalgorithms or other cryptographic services may be supported by the firstapplet and the second applet, respectively. Both the first applet andthe second applet are configured to protect received data and totransmit those protected data via the connection to the backend server.

For providing and operating the human machine interface, the secondapplet opens a user dialogue via the respective card application toolkit(i.e. the SIM/Java Card/USAT toolkit) and collects received transactiondata such as a payment amount and/or a PIN to authorize the payment astransaction. For this purpose, the respective toolkits matching therespective underlying cards (i.e. the SIM toolkit, the Java Card toolkitor the USAT (U SIM application toolkit)) provide the following commands:

-   -   DISPLAY TEXT    -   GET INKEY    -   GET INPUT    -   PLAY TONE    -   SET UP MENU    -   SELECT ITEM    -   SET UP IDLE MODE TEXT    -   LANGUAGE NOTIFICATION

In a further preferred embodiment, an edge cloud server located close tothe terminal device executes the application backend as the backendserver. The edge cloud server is arranged in a vicinity (i.e. in aspatial vicinity and/or in a logical vicinity) of the terminal deviceand, hence, allows for a particularly low round trip time (RTT) incompleting the transaction which further increases the acceptance of themethod.

Preferably, the mPOS application is operated using a cellular network asthe communication network and the edge cloud server is located close toa radio cell of the cellular network the terminal device is arranged in.The cellular network allows for carrying out the method practically atany place and, hence, strongly improves an applicability of the method.

As already indicated before, the application frontend is preferablybeing configured to authenticate a user of the terminal device via thehuman machine interface. For authenticating the user, the user mayprovide a personal key (e.g. a PIN) by operating the human machineinterface.

A third aspect of the invention refers to a system for operating a mPOSapplication. The system comprises a mPOS application, a terminal device,a UICC card, particularly a SIM card, an application frontend of themPOS application to be executed by the terminal device in conjunctionwith the UICC card, particularly the SIM card, a backend server, anapplication backend to be executed by the backend server and acommunication network for connecting the terminal device and the backendserver, wherein the terminal device, the UICC card, particularly the SIMcard, the application frontend, the backend server, the applicationbackend and the communication network are configured for togethercarrying out a method according to the invention.

As the system comprises a backend server and a terminal device (e.g. asmartphone or the like) and a mPOS application (e.g. implemented as asoftware program product) distributed among the devices, there is aplurality of possible applications of the invention.

The system may be created by simply installing the application backendon the backend server and the application frontend on the terminaldevice in conjunction with the UICC card.

According to the invention, the terminal device, the UICC card, theapplication frontend, the backend server, the application backend andthe communication network are configured for together carrying out amethod according to the invention. Due to the configuration, theinvolved devices together provide a method for completing thetransaction safely, i.e. protecting both sensitive data and ensuringhealth of the terminal device.

Preferably the communication network is a cellular network and thebackend server is an edge cloud server located close to a radio cell ofthe cellular network the terminal device is arranged in.

A fourth aspect of the invention refers to a terminal device with a UICCcard connected to the terminal device, wherein the terminal devicetogether with the UICC card, a backend server, a communication networkproviding a connection between the terminal device and the backendserver, and a distributed mPOS application, whose application frontendis to be executed on the terminal device and whose application backendis to be executed on the backend server, is configured to carry out amethod according to the invention.

It is an advantage of the invention that the transaction data, thefurther transaction data, the authorization and, eventually, additionaltransaction data are provided via an I/O interface provided by theterminal device in conjunction with a UICC card, particularly a SIMcard, connected to, particularly inserted in the terminal device. Themethod, hence, enables both the user and the further user operating theterminal device to avoid unintentionally presenting sensitive dataand/or a personal key to a third party. As a consequence, sensitive dataof the user and/or the further user is safely protected against fraudwhich results in an increased acceptance of the method.

Further advantages and configurations of the invention become apparentfrom the following description and the enclosed drawing.

It shall be understood that the features described previously and to bedescribed subsequently may be used not only in the indicatedcombinations but also in different combinations or on their own withoutleaving the scope of the present invention.

The invention is described in detail by means of an exemplary embodimentand with reference to the drawing. Like components are indicated by likereference numerals throughout the drawing.

FIG. 1 schematically shows a partial diagram of a system 1 for operatinga mPOS application. The system comprises a terminal device 11 and a UICCsmart card 12. The UICC smart card 12 is connected to the terminaldevice 11, particularly the UICC smart card 12 is inserted in theterminal device 11. The terminal device 11 is connected to acommunication network 13. The UICC smart card 12 connected to theterminal device 11 executes in interaction with the terminal device 11an application frontend 141 of a mPOS application 14. The applicationfrontend 141 provides, upon launch, an I/O interface with a humanmachine interface 142 displayed by a touchscreen of the terminal device11 and a machine-to-machine interface. During operation of the mPOSapplication 14, the human machine interface 142 allows receivingtransaction data associated with a transaction to be started, such as anamount of money corresponding to a price of a product to be sold, and apersonal key of a user 8 of the terminal device 11, such as a merchant,and/or a personal key of a further user 9, such as a merchant'scustomer. The machine-to-machine interface is provided by a CLF chip 143connected via SWP to the UICC smart card 12. The SWP interface to theCLF chip 143 of the terminal device 11 enables reading furthertransaction data, such as account data and authorization data from atransaction device 6, such as a credit card or debit card. The CLF chip143 provides a coupling coil 144 allowing the respective data to bereceived from the transaction device 6 by induction. Generally, SPW as acontact based protocol provides an interface between the CLF chip 143and the UICC card 12, such as a SIM card, and allows contactlesscommunication. Generally, the SIM card 12 comprises eight pins, numberedas C1 to C8. The C1 pin and the C5 pin are connected to the CLF chip 143for energy supply 145, i.e. to provide an operating voltage to the SIMcard 12, the C6 pin of the SIM card 12 is connected to the CLF chip 143for SWP support.

The SIM card 12 implements a first applet and a second applet. The firstapplet is configured to receive the further transaction data via themachine-to-machine interface, particularly from the CLF chip 143 of theterminal device 11 via the SWP protocol, and the second applet isconfigured to provide and operate the human machine interface 142 forcapturing the transaction data entered by the user 8 of the terminaldevice 11 and/or a personal key of the user 8 and/or a personal key of afurther user 9.

Both the first applet and the second applet are Java based applicationsthat run securely on the SIM card 12. The security is guaranteed by theunderlying Java Card technology.

Generally, known symmetric key algorithms, known asymmetric keyalgorithms or other cryptographic services may be supported by the firstapplet and the second applet, respectively. Both the first applet andthe second applet are configured to protect received data and totransmit those protected data to a backend server 10 via a connection131.

The backend server 10 connected to a communication network 13 executesthe application backend 140 of the transaction application 14. An edgecloud server located close to the terminal device 11 preferably executesthe application backend 140 as the backend server 10. When thetransaction application 14 is operated using a cellular network as thecommunication network 13, the edge cloud server may be located close toa radio cell 130 of the cellular network the terminal device 11 isarranged in.

For providing and operating the human machine interface 143, the secondapplet opens a user dialogue via a SIM toolkit (STK) and collects thereceived transaction data such as a payment amount and/or a PIN toauthorize the payment as transaction.

The first terminal device 11, the SIM card 12, the application frontend141, the backend server 10, the application backend 140 and thecommunication network 13 are configured for together carrying out thefollowing method, i.e. for executing the following steps:

-   -   the application frontend 141, for starting a transaction,        captures transaction data associated with the transaction to be        started via the human machine interface 143 and transmits a        transaction request indicating the transaction to be started and        comprising the transaction data to the application backend 140        via the connection 131,    -   the application backend 140, upon receipt of the transaction        request, transmits an authorization request to the application        frontend 141 via the connection 131,    -   the application frontend 141, upon receipt of the authorization        request, reads further transaction data via the        machine-to-machine interface from a transaction device 6        separate from the terminal device 11 and arranged close to the        terminal device 11, generates a transaction authorization        authorizing the requested transaction, adds the read further        transaction data to the transaction authorization and transmits        the transaction authorization to the application backend 140 via        the connection 131, and    -   the application backend 140, upon receipt of the transaction        authorization and the transaction data, verifies the transaction        authorization and completes the transaction.

While subject matter of the present disclosure has been illustrated anddescribed in detail in the drawings and foregoing description, suchillustration and description are to be considered illustrative orexemplary and not restrictive. Any statement made herein characterizingthe invention is also to be considered illustrative or exemplary and notrestrictive as the invention is defined by the claims. It will beunderstood that changes and modifications may be made, by those ofordinary skill in the art, within the scope of the following claims,which may include any combination of features from different embodimentsdescribed above.

The terms used in the claims should be construed to have the broadestreasonable interpretation consistent with the foregoing description. Forexample, the use of the article “a” or “the” in introducing an elementshould not be interpreted as being exclusive of a plurality of elements.Likewise, the recitation of “or” should be interpreted as beinginclusive, such that the recitation of “A or B” is not exclusive of “Aand B,” unless it is clear from the context or the foregoing descriptionthat only one of A and B is intended. Further, the recitation of “atleast one of A, B and C” should be interpreted as one or more of a groupof elements consisting of A, B and C, and should not be interpreted asrequiring at least one of each of the listed elements A, B and C,regardless of whether A, B and C are related as categories or otherwise.Moreover, the recitation of “A, B and/or C” or “at least one of A, B orC” should be interpreted as including any singular entity from thelisted elements, e.g., A, any subset from the listed elements, e.g., Aand B, or the entire list of elements A, B and C.

REFERENCE NUMERALS

-   1 system-   10 backend server-   11 terminal device-   12 UICC card, SIM card-   13 communication network-   130 radio cell-   131 connection-   14 mPOS application-   140 application backend-   141 application frontend-   142 human machine interface-   143 CLF chip-   144 coupling coil-   145 energy supply-   6 transaction device-   8 user-   9 further user

1. A method for operating a mobile Point-of-Sales (mPOS) application forexecuting a transaction, the method comprising: a Universal IntegratedCircuit Card (UICC) card connected to a terminal device executes ininteraction with the terminal device an application frontend of the mPOSapplication that provides, upon launch, an I/O interface with a humanmachine interface displayed by a touchscreen of the terminal device anda machine-to-machine interface; and the application frontend, forstarting a transaction, captures transaction data associated with thetransaction to be started via the human machine interface, reads furthertransaction data via the machine-to-machine interface from a transactiondevice separate from the terminal device and arranged close to theterminal device, generates a transaction authorization authorizing therequested transaction, and transmits the transaction authorization, thetransaction data and the further transaction data via a connection to aremote backend server for completing the transaction.
 2. The methodaccording to claim 1, wherein reading further transaction data via themachine-to-machine interface comprises wirelessly reading the furthertransaction data from the transaction device using near fieldcommunication (NFC) or Bluetooth.
 3. The method according to claim 1,wherein reading further transaction data via the machine-to-machineinterface comprises reading account data as the further transaction dataand authorization data from a credit card or a debit card as thetransaction device, and wherein a payment is completed as thetransaction.
 4. The method according to claim 1, wherein the UICC cardcomprises a card application toolkit (CAT) for building up the humanmachine interface.
 5. The method according to claim 1, whereingenerating the transaction authorization comprises capturing a personalkey via the human machine interface and adding the captured personal keyto the transaction authorization.
 6. The method according to claim 1,wherein the UICC card implements, using at least one encryption key, atleast one secure data channel on the connection.
 7. A method foroperating a mobile Point-of-Sales (mPOS) application for executing atransaction, the method comprising: a backend server connected to acommunication network executes an application backend of the mPOSapplication; a Universal Integrated Circuit Card (UICC) card inserted ina terminal device that is connected to the communication network via aconnection executes in interaction with the terminal device anapplication frontend of the mPOS application that provides, upon launch,an I/O interface with a human machine interface displayed by atouchscreen of the terminal device and a machine-to-machine interface;the application frontend, for starting a transaction, capturestransaction data associated with the transaction to be started via thehuman machine interface and transmits a transaction request indicatingthe transaction to be started and comprising the transaction data to theapplication backend via the connection; the application backend, uponreceipt of the transaction request, transmits an authorization requestto the application frontend via the connection; the applicationfrontend, upon receipt of the authorization request, reads furthertransaction data via the machine-to-machine interface from a transactiondevice separate from the terminal device and arranged close to theterminal device, generates a transaction authorization authorizing therequested transaction, adds the read further transaction data to thetransaction authorization and transmits the transaction authorization tothe application backend via the connection; and the application backend,upon receipt of the transaction authorization and the transaction data,verifies the transaction authorization and completes the transaction. 8.The method according to claim 7, wherein reading further transactiondata via the machine-to-machine interface comprises wirelessly readingthe further transaction data from the transaction device using nearfield communication (NFC) or Bluetooth.
 9. The method according to claim7, wherein reading further transaction data via the machine-to-machineinterface comprises reading account data as the further transaction dataand authorization data from a credit card or a debit card as thetransaction device, and wherein a payment is completed as thetransaction.
 10. The method according to claim 9, wherein themachine-to-machine interface is implemented as a Single Wire Protocol(SWP) interface to a contactless frontend (CLF) chip of the terminaldevice for reading the account data and the authorization data from thecredit card or debit card.
 11. The method according to claim 7, whereinthe UICC card comprises a card application toolkit (CAT) for building upthe human machine interface.
 12. The method according to claim 7,wherein generating the transaction authorization comprises capturing apersonal key via the human machine interface and adding the capturedpersonal key to the transaction authorization.
 13. The method accordingto claim 12, wherein verifying the transaction authorization comprisesverifying whether the captured personal key matches the transactiondevice and considering the transaction to be authorized when thecaptured personal key matches the transaction device.
 14. The methodaccording to claim 7, wherein the UICC card implements, using at leastone encryption key, at least one secure data channel on the connection.15. The method according to claim 1, wherein the UICC card implements afirst applet and a second applet, the first applet being configured toreceive the further transaction data via the machine-to-machineinterface, particularly from a contactless frontend (CLF) chip, and thesecond applet being configured to provide and operate the human machineinterface for capturing the transaction data entered by a user of theterminal device and/or a personal key of the user and/or a personal keyof a further user.
 16. The method according to claim 2, wherein an edgecloud server located close to the terminal device executes theapplication backend as the backend server.
 17. The method according toclaim 16, wherein the mPOS application is operated using a cellularnetwork as the communication network, wherein the edge cloud server islocated close to a radio cell of the cellular network, and wherein theterminal device is arranged in the cellular network.
 18. A terminaldevice for a communication network, with a UICC card connected to theterminal device and being configured for carrying out the methodaccording to claim
 1. 19. A system for operating a mobile Point-of-Sales(mPOS) application, comprising: a terminal device; a UniversalIntegrated Circuit Card (UICC) card inserted in the terminal device; anda backend server; wherein the backend server is connected to acommunication network and is configured to execute an applicationbackend of the mPOS application; wherein the UICC card is connected tothe communication network via a connection and is configured to executein interaction with the terminal device an application frontend of themPOS application that provides, upon launch, an I/O interface with ahuman machine interface displayed by a touchscreen of the terminaldevice and a machine-to-machine interface; wherein the applicationfrontend is configured to, for starting a transaction, capturetransaction data associated with the transaction to be started via thehuman machine interface and transmit a transaction request indicatingthe transaction to be started and comprising the transaction data to theapplication backend via the connection; wherein the application backendis configured to, upon receipt of the transaction request, transmit anauthorization request to the application frontend via the connection;wherein the application frontend is configured to, upon receipt of theauthorization request, read further transaction data via themachine-to-machine interface from a transaction device separate from theterminal device and arranged close to the terminal device, generate atransaction authorization authorizing the requested transaction, add theread further transaction data to the transaction authorization andtransmit the transaction authorization to the application backend viathe connection; and wherein the application backend is configured to,upon receipt of the transaction authorization and the transaction data,verify the transaction authorization and complete the transaction. 20.The system according to claim 19, wherein the communication network is acellular network, the backend server is an edge cloud server locatedclose to a radio cell of the cellular network, and wherein the terminaldevice is arranged in the cellular network.